Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Break long lines in commands #261

Closed
wants to merge 1 commit into from
Closed

Break long lines in commands #261

wants to merge 1 commit into from

Conversation

bkmgit
Copy link
Contributor

@bkmgit bkmgit commented Apr 3, 2024

If this pull request addresses an open issue on the repository, please add 'Closes #NN' below, where NN is the issue number.

Closes #260

Please briefly summarise the changes made in the pull request, and the reason(s) for making these changes.

Break long lines with command text so that they can be read without horizontal scrolling.

If any relevant discussions have taken place elsewhere, please provide links to these.

@github-actions GitHub Actions
Copy link

github-actions bot commented Apr 3, 2024 •
edited
Loading

Thank you!

Thank you for your pull request 😃

🤖 This automated message can help you check the rendered files in your submission for clarity. If you have any questions, please feel free to open an issue in {sandpaper}.

If you have files that automatically render output (e.g. R Markdown), then you should check for the following:

  • 🎯 correct output
  • 🖼️ correct figures
  • ❓ new warnings
  • ‼️ new errors

Rendered Changes

🔍 Inspect the changes: https://github.com/LibraryCarpentry/lc-shell/compare/md-outputs..md-outputs-PR-261

The following changes were observed in the rendered markdown documents:

 05-counting-mining.md | 12 ++++++++----
 md5sum.txt            |  2 +-
 2 files changed, 9 insertions(+), 5 deletions(-)
What does this mean?

If you have source files that require output and figures to be generated (e.g. R Markdown), then it is important to make sure the generated figures and output are reproducible.

This output provides a way for you to inspect the output in a diff-friendly manner so that it's easy to see the changes that occur due to new software versions or randomisation.

⏱️ Updated at 2024-04-03 14:19:36 +0000

github-actions bot pushed a commit that referenced this pull request Apr 3, 2024
@actions-user
differences for PR #261
fb54414
@kaitlinnewson
Copy link
Member

Closing, see #263

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Break long lines with commands
2 participants
@bkmgit @kaitlinnewson